Re: When pg_rewind success, the database can't startup - Mailing list pgsql-bugs

From hemin
Subject Re: When pg_rewind success, the database can't startup
Date
Msg-id 7295DA46-F7BB-4F6A-8246-40C034B401DC@ww-it.cn>+ECBE3386FF7912CB
Whole thread Raw
In response to Re: When pg_rewind success, the database can't startup  (Michael Paquier <michael@paquier.xyz>)
List pgsql-bugs
    OK,the max_wal_size use the default value 1G, I try it later, and report the result to you, thanks.


    何敏

    Call: 185.0821.2027 | Fax: 028.6143.1877 | Web: w3.ww-it.cn
    成都文武信息技术有限公司|ChengDu WenWu Information Technology Inc.|WwIT
    地址: 成都高新区天府软件园B区7栋611 |邮编:610041

    在 18/6/19 下午16:00,“Michael Paquier”<michael@paquier.xyz> 写入:

        On Tue, Jun 19, 2018 at 03:56:15PM +0800, hemin wrote:
        > I do not checkpoint before running pg_rewind, because the checkpoint
        > of rewound primary node is obviously slow than the promoted standby,
        > But I will try it later.

        You need to run the checkpoint on the promoted standby.  That's actually
        a critical thing to do to ensure consistency..  Of course this depends
        on how you set max_wal_size.
        --
        Michael







pgsql-bugs by date:

Previous
From: Michael Paquier
Date:
Subject: Re: When pg_rewind success, the database can't startup
Next
From: PG Bug reporting form
Date:
Subject: BUG #15248: pg_upgrade fails when a function with an emptysearch_path is encountered